home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 25
/
Cream of the Crop 25.iso
/
bbs
/
outil179.zip
/
PHATCH.DOC
< prev
next >
Wrap
Text File
|
1997-04-30
|
3KB
|
87 lines
PHATCH
PHATCH is an Opus 1.79 specific pre-processor for HATCH.EXE. In other
words, you run it before running HATCH, because HATCH is not aware of
the new file database structure in Opus 1.79, and you still need to
add new file names and descriptions to your file database.
It enters a hatched file to your Opus 1.79 file database and invokes
HATCH to generate the corresponding TIC files. A companion program
for PTIC, PHATCH uses the same TIC.CFG file and the same requirements.
It uses the same rules as HATCH for finding the TIC.CFG file.
Firstly, it looks for the command line switch /C, then for the
environment variable TIC, and then for TIC.CFG in the current
directory.
Command Line Switches:
======================
/a file echo area name
/c TIC configuration file name
/d file description (must be last arg)
/f name of file to HATCH
/h do NOT execute hatch.exe
/l log file name
/ON no wait
/Rxx release in xx days
/v verbose gives very detailed output (for debugging)
Most of the above params are the same as for HATCH.
Preparing TIC.CFG:
==================
Comment or delete all the FILES.BBS statements like ListFmt and
ListName from your TIC.CFG file.
Setting The Environment:
========================
Since Opus allows the system dat files and the user file to be located
in a directory other than the Opus home directory, support has been
added to look up these paths in the Opus prm file.
Set up an environment variable labeled OPUS, and specify the full
pathname of the prm file as follows:
SET OPUS=C:\OPUS\BBS.PRM
If your environment space is cramped, you may leave off the .PRM
suffix, the program will add it. BTW, Doug and I are making the OPUS
environment variable a standard for all the OPUS utilities.
If the OPUS environment variable is not set, the program will look in
the current working directory for USER.DAT and SYSMSG.DAT. If either
file is not found, it will then look for BBS.PRM and look up the paths
in there. If none of the above are found, the program will fail.
What Happens:
=============
When you invoke PHATCH, here's what happens:
1. PHATCH reads your TIC.CFG.
2. PHATCH reads your input (via the command line switches or the
interactive prompts) to post the file and prepare a command
line instruction for HATCH.
3. HATCH is invoked to generate the corresponding TIC files
and post the entry to the default file listing Files.Bbs.
4. PHATCH returns (having already read the TIC.CFG) awaiting
fresh input. You may default the current file area or enter
a new one.
5. PHATCH exits when you hit <ENTER> with no fresh input.
John Valentyn 1:114/5@fidonet.org